5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
- Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-2: Getting Started

Input Keymaps


The specific keys users press to perform each input-related activity is installation-specific. The key on the keyboard (or other input device) that controls each operation and option is mapped according to the devices at your installation. The resulting keymap tells APPX which keys control which operations. Refer to your system administrator for information about establishing customized keymaps in APPX.

The Data Entry Keymap

The data entry keymap provides capabilities relevant to entering, displaying, and manipulating information on the screen. For input processes, the user is always in the data entry keymap.

In the data entry keymap, only items that have an entry level less than or equal to the current entry level are visible and modifiable on the screen. For example, when APPX first displays the screen, only items with an entry level of 1 are visible. After the user selects return, the items for entry level 2 become visible. This process continues until the entry levels for all items on the image are complete.

You can also establish that an item associated with a specific entry level is non-modifiable either by completing specifications in the image editor, or by explicitly defining a NO INPUT statement.

Application Design Manual                                         "Powered by Appx Software"

270

©2006 By APPX Software, Inc. All Rights Reserved